It looks like you need to regenerate the trace info for the native build. See the instructions here: https://github.com/nasa/fpp/tree/main/compiler#building-native-binaries.

Another issue I see is that the code generator is generating an empty TypesAc.cpp file. I think we should suppress the generation of this file. Does that require any changes to the CppDoc framework?

@bocchino You may need to do the trace updates again, I can't install GraalVM for Java11 since the only version available from Homebrew is jdk23 and the SDKMAN/official installation method seems to only have 17, 21, and 23.

We may also want to consider updating the Java version or putting the trace updates in CI

We may also want to consider updating the Java version or putting the trace updates in CI

Noted. The trace updates are supposed to be in CI, but they have never worked, and instead of wrangling CI I have just updated them manually. @LeStarch do you see any issue with updating the FPP Java environment from Java 11 to Java 17? We would need to do this in the GitHub actions.

I opened an issue on upgrading Java: #605.

As discussed, I'll resolve the conflict in the native image trace file.

I resolved the conflict. It looks like there is a test failure for fpp-to-cpp/test/struct/alias_type.fpp. A map lookup is failing.

I added some scala tests and found an issue in the commonType() implementation for type aliases. We now compute the "lowest common ancestor" of the type alias tree as the common type.

For example:

type T

type A1 = T
type A2 = A1
type A3 = A1

commonType(A2, A3) => A1 not the underlying type T since A1 is more descriptive. I also had to update the spec to include this change